- What is the problem?
Autopilot doesn’t have a way to interrupt and start over with an already-started Autopilot update.
- Why is it a problem?
There are times when Autopilot will be manually started, but then the user needs to stop it to change a configuration. Sometimes this is just accidental and sometimes a configuration requirement will appear at the time there is a current Autopilot update happening.
- How do you solve the problem today?
I don’t. I just wait out the currently-running process and then I go in and make the config change and run it again.
- How would you ideally solve the problem?
A big red “Stop” button. 
- How big is the problem (business impact, frequency of impact, who is impacted)
It reduces efficiency if we have to wait for a misconfigured Autopilot to finish running before we can do anything about the misconfiguration. Also, if a user remembers in mid-run that something ought to have been changed or it would risk a problem with a Dev, Test, or Live environment, it would be helpful to interrupt the process.